Repository navigation
Conversation
🎩 PreviewA preview build has been created at: |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Report browser editor-control reconnect errors once per connection outage instead of notifying on every Socket.IO
connect_error(websocket/xhr polling retries).Reset the notification latch on successful reconnect. Preserve initial connection rejection, automatic retry behavior, stale-client suppression and existing diagnostic logging. Each host reports independently; no global state is introduced.
Validation
32 focused tests pass across remoteEnvHost and connectRemoteEnvWithRefresh. TypeScript and targeted ESLint pass. Added tests for repeated mixed transport errors, recovery/new outage, stale disconnect callbacks and initial connect failure.
Scope
Confirmed the repeated-notification code path while investigating production project
01a1b305029cbb40e304. This prevents retry spam; it does not claim to repair the underlying transport/proxy failure, which has not been reproduced. A polling handshake to the project's proxy succeeded during read-only investigation.